Add check for the existence of EESSI_SITE_SOFTWARE_PATH in EESSI-extend#235
Add check for the existence of EESSI_SITE_SOFTWARE_PATH in EESSI-extend#235casparvl wants to merge 2 commits into
EESSI_SITE_SOFTWARE_PATH in EESSI-extend#235Conversation
…needed if we make this location configurable thourhg EESSI_SITE_SOFTWARE_PREFIX as is done in EESSI#232
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
Add check for the existence of the
EESSI_SITE_SOFTWARE_PATH. This is needed if we make this location configurable throughEESSI_SITE_SOFTWARE_PREFIXas is done in #232Edit: hmmm, this check was requested by @ocaisa . But now that I see the CI failing because the dir doesn't exist, I'm wonderig... this means that sites would have to precreate the dir, before they even set
EESSI_SITE_INSTALL=1, or the module will just flat-out fail to load. Is that what we want? If that dir does not exist whenEESSI-extendis loaded, how bad is that? Won't EasyBuild just try to create it? It looks like it...